Repository navigation
Conversation
The api's other OpenTelemetry packages (@opentelemetry/core, resources) are already on 2.x, and the tree already resolves sdk-trace-base 2.12.0. The 1.x dev dependency pulled in a second copy of core, resources, sdk-trace-base and semantic-conventions. The only user is the AI telemetry test, which already uses the constructor API that 2.x requires.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
🔵 Tier 2 — Low RiskSmall, isolated change with no API route or data model modifications. Why this tier:
Review process: AI review + quick human skim (target: 5–15 min). Reviewer validates AI assessment and checks for domain-specific concerns. Stats
|
PR Review✅ No issues found. |
Duplicate code analysisNo new duplicate code introduced by this PR. jscpd compared this branch against |
Deep Review✅ No critical issues found. This is a dev-only dependency bump:
No P0/P1, P2, or P3 findings surfaced after re-grading. Reviewers (3): correctness, project-standards, previous-comments. |
E2E Test Results✅ All tests passed • 466 passed • 1 skipped • 1035s
Tests ran across 4 shards in parallel. |
Summary
Move the
@opentelemetry/sdk-trace-basedev dependency inpackages/apifrom^1.30.1to^2.8.0.@opentelemetry/core,@opentelemetry/resources) are already on 2.x, and the tree already resolvessdk-trace-base2.12.0. The new range reuses that copy.core,resources,sdk-trace-baseandsemantic-conventions. Removing it also removes@opentelemetry/core1.30.1, which is flagged by GHSA-8988-4f7v-96qf (fixed in 2.8.0).src/utils/__tests__/aiTelemetry.test.ts, which already passes span processors through the constructor, the API 2.x requires. No code changes needed.How to test locally or on Vercel
yarn installcd packages/api && npx tsc --noEmit: passes.npx jest src/utils/__tests__/aiTelemetry.test.ts: 6 tests pass.Dev dependency only, so no changeset.
🤖 Generated with Claude Code